fix!: Default ListenerClass externalTrafficPolicy to null #347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Part of stackabletech/issues#770
Pulls in stackabletech/operator-rs#1107
IONOS loadbalances don't support the
Localtraffic policy. so demos and tests didn't work put of the box on IONOS.This PR changes to safer default (
null), see the release notes below.Release notes
.spec.externalTrafficPolicytonullto improve LoadBalancer support across various Kubernetes environments.Previously, ListenerClasses used
Localby default, which can be more performant, but needs to be supported by the LoadBalancer.Setting this field no
nullforwards the defaulting to the Kubernetes API server, which internally defaults toCluster.This change can result in degraded performance when the field was previously unconfigured, therefore it is marked as a breaking change.
The field can explicitly be set to
Localto restore the old behavior.See https://github.com/stackabletech/listener-operator/pull/347[listener-operator#347].
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker